Repository navigation
Conversation
Added the feature of hardware enabled stack guard. The exception is raised on stack overflow for the tasks. This is completely monitored and controlled by the hardware configuration.
juitem
left a comment
juitem
left a comment
There was a problem hiding this comment.
Would you please seperate hello_main.c
from thic commit?
Let's push MPU application testing features be out ot hello example
btheosam
left a comment
btheosam
left a comment
There was a problem hiding this comment.
Few questions;
- Stack creation of idle task is not through up_createstack(), hope idle tak's stack is also acommodated?
- How exception is triggered? is it when stack guard is overwritten by different task or any part of stack is overwittern by another task?
- Does these changes take care of both task as well thread stack?
|
@btheosam |
|
@juitem |
|
@ALL committing stack guard patches. |
mbedTLS 3.4 builds fail because MBEDTLS_CERTS_C is unavailable and key parsing requires RNG arguments. Drop the obsolete feature check and export tls_handshake_server in the fallback. Seed CTR_DRBG before key parsing and pass its RNG callback and context. [Result] ``` TASH>>tls_seclink TASH>>-- [TLS SECLINK TEST] START -- Hello, TLS Server Test [SERVER] . Seeding the random number generator...[SERVER] ok [SERVER] . Loading the server cert. and key...[SERVER] ok [SERVER] . Bind on https://localhost:4433/ ...[SERVER] ok [SERVER] . Setting up the SSL data....[SERVER] ok [SERVER] . Waiting for a remote connection ...Hello, TLS Clinet Test [CLIENT] . Seeding the random number generator...[CLIENT] ok [CLIENT] . Loading the CA root certificate ...[CLIENT] ok (0 skipped) [CLIENT] . Connecting to tcp/127.0.0.1/4433...[SERVER] ok [SERVER] . Performing the SSL/TLS handshake...[CLIENT] ok [CLIENT] . Setting up the SSL/TLS structure...[CLIENT] ok [CLIENT] . Performing the SSL/TLS handshake...[SERVER] ok [SERVER] < Read from client: [CLIENT] ok [CLIENT] . Verifying peer X.509 certificate...[CLIENT] ok [CLIENT] > Start Packet Perfomance Test [28] [CLIENT] Try Write #1 [ 64 bytes ] --> [CLIENT] Try Write #1 Done <-- [CLIENT] Try Write #2 [ 128 bytes ] --> [CLIENT] Try Write #2 Done <-- [CLIENT] Try Write #3 [ 256 bytes ] --> [CLIENT] Try Write #3 Done <-- [CLIENT] Try Write #4 [ 512 bytes ] --> [CLIENT] Try Write #4 Done <-- [CLIENT] Try Write Samsung#5 [ 1024 bytes ] --> [CLIENT] Try Write Samsung#5 Done <-- [CLIENT] Try Write Samsung#6 [ 2048 bytes ] --> [CLIENT] Try Write Samsung#6 Done <-- [CLIENT] Try Write Samsung#7 [ 4096 bytes ] --> [CLIENT] Try Write Samsung#7 Done <-- [CLIENT] < Read from server: [SERVER] > Start Packet Perfomance Test [28] [SERVER] . Closing the connection...[SERVER] ok [CLIENT] 64 bytes read [CLIENT] 128 bytes read [CLIENT] 256 bytes read [CLIENT] 512 bytes read [CLIENT] 1024 bytes read [CLIENT] 2048 bytes read [CLIENT] 4096 bytes read [CLIENT] End : 0 -- [SERVER] End : 0 -- -- [TLS SECLINK TEST] Success -- ------------------------------------------------------------------------------------------- | 64 | 128 | 256 | 512 | 1024 | 2048 | 4096 | ------------------------------------------------------------------------------------------- Encrypt | 1020 | 1290 | 2190 | 3840 | 21870 | 26700 | 26040 | Decrypt | 990 | 1230 | 1950 | 3570 | 6720 | 12750 | 25170 | ------------------------------------------------------------------------------------------- -- [TLS SECLINK TEST] DONE -- ``` Co-authored-by: Codex Signed-off-by: seokhun-eom <seokhun.eom@samsung.com>
Added the feature of hardware enabled stack guard. The exception is raised on stack overflow for the tasks. This is completely monitored and controlled by the hardware configuration.